Repository navigation
fix(workspace): show Docker build progress without default timeouts - #1175
Open
crispinhu27 wants to merge 1 commit into
Open
crispinhu27 wants to merge 1 commit into
crispinhu27 wants to merge 1 commit into
Conversation
Robert0622
reviewed
Nov 21, 2026
Robert0622
left a comment
Collaborator
There was a problem hiding this comment.
在 8db9ac23 上,用 iOA DeepSeek V4.1 Flash 连真实 Runner 验证了冷构建进度和中途停止。刷新对话仍能看到正在执行的步骤,停止后约 0.4 秒观测到 Docker CLI 退出。前端 464 项测试、Go 工作区相关回归和 GitHub validate、e2e、platform 均通过。多阶段进度有一处可复现的问题,详见行内评论。
| if step[3] == "FROM" { | ||
| return "准备基础镜像" | ||
| } | ||
| return fmt.Sprintf("执行 Dockerfile 第 %s/%s 步", step[1], step[2]) |
Collaborator
There was a problem hiding this comment.
[P2] 保留多阶段 Dockerfile 的阶段标识
实测 BuildKit 的串行阶段先输出 #5 [compile 2/2] RUN …,再输出 #6 [package 2/2] RUN …。两条日志都映射成 执行 Dockerfile 第 2/2 步。用 PR 的解析器重放真实日志时,ensureDockerImage 的文本去重条件会丢掉 package 的进度事件。夹具进入 package 后又运行约 22 秒,对话里的步骤不会更新。建议把阶段名或稳定的阶段编号带进显示标签和去重键,继续省略指令参数。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Scope
Compatibility
Ship the platform and connected Runner together so workspace preparation can receive cancellation. Existing explicit Docker build limits still apply.
Validation
bash scripts/build-chatbot.shbuilt the frontend and passed 464 tests.go test -p=2 ./internal/httpapi ./internal/runner ./internal/runtime ./internal/engine -run 'Test(RunnerWorkspace|RunnerConversationWorkspace|ConversationWorkspace|DockerBuild)' -count=1 -timeout=120sandgo test ./internal/procwatch -count=1 -timeout=120spassed in local Docker.python3 scripts/check-public.pyandgit diff --checkpassed.main, a cold workspace image built through a local connected Runner with a cached Node base image and a deterministic test CLI. One Dockerfile step downloaded a 61.5 MiB Go SDK at about 64 KiB/s for 16m 20s. The conversation still showed that step at 10m 10s and 15m 10s. BuildKit exported the image after 16m 35s. The resulting workspace rango versionand executed the compiled test program.Safety